Home
Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
Migrating an existing IBM® installation to HCL Launch

Upgrading and migrating
Learn how to upgrade HCL Launch elements, including the server, agents, and how to migrate data.
- Testing an upgrade
  Before you upgrade your production HCL Launch server, for best results, perform a test upgrade, verify the challenges you are facing, and resolve them before performing an actual upgrade.
- Upgrading the server
  You can upgrade the HCL Launch server to incorporate to a later version. Always upgrade agents, agent relays in addition to upgrading the server. Upgrading the server, agents, agent relays are each completed independently. Unless specified, upgrade the server before you upgrade the agents.
- Upgrading high-availability installations
  All servers that are configured for the HA feature must be on the same version. Thus, all servers must be upgraded at the same time.
- Upgrading agents
  In most cases, you upgrade agents from the server interface, but you can also upgrade the agents from the command line. Always upgrade agents and agent relays in addition to upgrading the server.
- Upgrading agent relays
  In most cases, you upgrade agents relays from the command line, but starting from 7.0.4.2 version, you can upgrade the server from the interface. Always upgrade agents and agent relays in addition to upgrading the server.
- Migrating the server database
  The server installation files include a script that migrates the server database from Derby to another database system. You can not migrate from any database other than Derby.
- Migrating the server to Kubernetes/Openshift
  You can migrate your HCL Launch server from an on-premises production installation to a containerized instance that runs in a Kubernetes or Openshift cluster.
- Migrating an existing IBM® installation to HCL Launch

Migrating an existing IBM® installation to HCL Launch

About this task

About this task

HCL Launch supports the ability to migrate from the IBM® vendor type to the HCL vendor type.

Note: The HCL installer must be version 7.0.2.0 or greater, the installed IBM® server can be any version so long as it is less than the version that will be upgraded to.

Procedure

Procedure

Download the HCL installer for the same version that the IBM® server is.
Shut down the IBM® server.
Run the installer, direct it to the existing installation. You will be notified that a server already exists at the location, and that proceeding will cause the server to be upgraded.

You will also see a new message:
If y is given as an answer the installer will then automatically convert the installation to the HCL vendor type and proceed with the rest of the upgrade process.
A prompt will request HCL licensing information. If migrating a silent mode installer, in the passed in properties answer file please include "license.server.url=" and have the value point to a valid HCL license server.
Start up the server.

Results

Results

IBM® specific RCL license libraries are replaced with HCL FlexNet license libraries.
Set_env file is modified to load HCL license jars instead of IBM® license jars.
Every agent on the server has a license type other than Unlicensed will be given the Authorized license type – the only license type that HCL servers support.
HCL specific CSS and JavaScript license files will swap out IBM® specific files.
- As consequence the server will use the HCL specific branding if you are migrating version 7.1.0.0 or newer.